Reprogramming a field programmable device on-demand

ABSTRACT

Examples of techniques for reprogramming a field programmable device on demand are disclosed. According to aspects of the present disclosure, a computer-implemented method may include: identifying a first field programmable device as being over utilized; responsive to identifying the first field programmable device that is over utilized, identifying a second field programmable device that is underutilized; determining whether to reprogram the second field programmable device; responsive to determining to reconfigure the second field programmable device, stopping the second field programmable device from performing a workload; moving the workload to another field programmable device configured to perform the workload; and reprogramming the second field programmable device.

DOMESTIC PRIORITY

This application is a continuation application of the legally relatedU.S. Ser. No. 15/271,728 filed Sep. 21, 2016, the contents of which areincorporated by reference herein in their entirety.

BACKGROUND

The present application generally relates to field programmable devicesand, more particularly, to reprogramming a field programmable device ondemand

Special purpose processing units are gaining popularity due to theirhigh performance. In some situations, hardware manufacturers have begunadding field-programmable device-based special purpose processing unitsto computing systems to improve performance and cost to run a specialworkload. A field-programmable device (FPD) such as a field programmablegate array (FPGA), a programmable read-only memory (PROM), or aprogrammable logic device (PLD) provides more flexible compared totraditional integrated circuit manufacturing by allowing updating offunctionality after shipping the computing system (i.e., while thecomputing system is in the field). The update of functionality of an FPDis currently limited to firmware upgrades, service related tasks, or ahuman decision to re-purpose an FPD.

SUMMARY

According to examples of the present disclosure, techniques includingmethods, systems, and/or computer program products for reprogramming afield programmable device on demand are provided. An example method mayinclude: identifying, by a processing device, a first field programmabledevice as being over utilized, wherein the first field programmabledevice is configured with a first set of computer readable instructionsto perform a first workload type; responsive to identifying the firstfield programmable device that is over utilized, identifying, by theprocessing device, a second field programmable device that isunderutilized, wherein the second field programmable device isconfigured with a second set of computer readable instructions differentfrom the first set of computer readable instructions to perform a secondworkload type; determining whether to reprogram the second fieldprogrammable device with the first set of computer readableinstructions; responsive to determining to reconfigure the second fieldprogrammable device with the first set of computer readableinstructions, stopping the second field programmable device fromperforming a workload of the second workload type; moving the workloadof the second workload type to another field programmable deviceconfigured to perform the workload of the second workload type; andreprogramming the second field programmable device with the first set ofcomputer readable instructions to perform the first workload type.

Additional features and advantages are realized through the techniquesof the present disclosure. Other aspects are described in detail hereinand are considered a part of the disclosure. For a better understandingof the present disclosure with the advantages and the features, refer tothe following description and to the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter which is regarded as the invention is particularlypointed out and distinctly claimed in the claims at the conclusion ofthe specification. The foregoing and other features, and advantagesthereof, are apparent from the following detailed description taken inconjunction with the accompanying drawings in which:

FIG. 1A and FIG. 1B illustrate a block diagram of a processing systemfor reprogramming a field programmable device on demand according toexamples of the present disclosure;

FIG. 2 illustrates a flow diagram of a method 200 for reprogramming afield programmable device on demand according to examples of the presentdisclosure;

FIG. 3 illustrates a flow diagram of a method 200 for reprogramming afield programmable device on demand according to examples of the presentdisclosure; and

FIG. 4 illustrates a block diagram of a processing system forimplementing the techniques described herein according to examples ofthe present disclosure.

DETAILED DESCRIPTION

Although previous approaches utilize updating the functionality of afield-programmable device (FPD), such updating is limited. Consequently,FPDs have not been fully exploited for their dynamic capability. Variousimplementations are described below by referring to several examples ofreprogramming an FPD (e.g., a field-programmable gate array (FPGA), aprogrammable read-only memory (PROM), or a programmable logic device(PLD)) on demand. Some computing system manufacturers ship computingsystems with a multiple FPDs included in the computing system. The FPDsmay be enabled by a manual user request or by an automatic request by asoftware program executing on the computing system. The FPDs may also beassigned to perform a specific workload type by being programmed with aparticular set of computer readable instructions for performing thespecific workload. The present techniques provide for reprogramming anFPD on demand by loading a different set of computer readableinstructions to the FPD to cause the FPD to perform a different specificworkload type.

In some implementations, the present techniques provide improvedfunctioning of the computing system by providing additional systemresources (i.e., additional FPDs) on demand by reprogramming an FPD,such as in response to high demand for resources. Additionally, thepresent techniques reduce system resource demands on the generalprocessor of the computing system by enabling FPDs to performspecialized tasks (e.g., encoding/decoding of data, data encryption,data analytics, etc.).

The present techniques also provide the ability to monitor and track thetime that an FPD is enabled and performing a specific workload type sothat a user may be billed for the time. In addition, the presenttechniques enable increased system performance by updating/reprogrammingthe FPD to perform different specialized tasks, thereby reducing theresource demands on the computing system's native resources (i.e.,memory, general processor, etc.). These and other advantages will beapparent from the description that follows.

FIG. 1A illustrates a block diagram of a processing system 100 forreprogramming an FPD on demand according to examples of the presentdisclosure. The processing system 100 includes a processor 102 that maybe a general purpose processor and a memory 104 associated with theprocessor 102. The processor 102 is responsible for executing computerreadable instructions stored in the memory 104. For example, theprocessor 102 may execute an operating system and one or moreapplications running within the operating system.

In some situations, specialized tasks may be offloaded onto a fieldprogrammable device. The FPD may execute computer readable instructions(i.e., logic) to perform a specialized task, such as encoding/decodingof data, data encryption, data analytics, or other tasks that aresuitable for execution on a field programmable device. By offloadingthese specialized tasks to field programmable devices, the processingsystem 100 and its processor 102 is free to perform other tasks.

In the example of FIG. 1A, the processing system 100 includes six fieldprogrammable devices (e.g., FPD 110, FPD 112, FPD 114, FPD 116, FPD 118,and/or FPD 120). FPD 110 and FPD 112 are configured with Logic A, whichrepresents logic for executing a first specialized task (i.e., a firsttype of workload). FPD 114 and FPD 116 are configured with Logic B,which represents logic for executing a second specialized task (i.e., asecond type of workload). FPD 118 and FPD 120 are configured with LogicC, which represents logic for executing a third specialized task (i.e.,a third type of workload).

If the load on FPD 110 and/or FPD 112 becomes too high (i.e., FPD 110and/or FPD 112 becomes over utilized), one the remaining FPDs may bereprogrammed with Logic A to perform first specialized tasks (i.e.,workloads of the first type). In one example as illustrated in FIG. 1A,one or both of FPD 114 and FPD 116 are identified as being overutilized. An FPD may be overutilized if its performance drops below athreshold, if it fails to execute a workload in a certain amount oftime, if the demand on the FPD exceeds a threshold, if the delay inexecuting a workload exceed certain amount of time, if the number ofrequests on behalf of a workload waiting for FPD exceed certain limit,or for other suitable reasons.

Since one or both of FPD 114 and FPD 116 are over utilized, theprocessing system 100 identifies another one of the remaining FPDs asbeing underutilized. To determine if an FPD is underutilized, theprocessing system may determine that current demand on the FPD does notnecessitate the need for the FPD, that the FPD has an amount of workbelow a threshold, or for other suitable reasons. If none of the otherFPDs are underutilized, the other FPDs are not available forreprogramming, and each of the FPDs continues executing tasks asappropriate.

However, if one of the other FPDs is underutilized, the underutilizedFPD may be reprogrammed In the present example of FIG. 1A, FPD 118 isidentified as being underutilized. In this example, FPD 118 is thenreprogrammed with Logic B so that FPD 118 may execute a workload of thesecond type. To reprogram FPD 118, the processing system may stop FPD118 from performing a workload of the third workload type and then movethe workload of the third workload type to another field programmabledevice configured to perform the workload of the third workload type(e.g., FPD 120).

In another non-limiting example, an FPD can be identified to bereprogrammed with Logic B so that FPD 118 may execute a workload of thesecond type when FPD 118 is highly utilized but running lower priorityworkloads of a first type compared to the workload of second type.

Once the work is moved, the processing system 100 may bring FPD 118offline, which may include entering a programming state. When the FPD118 is online, the FPD 120 is responsible to process all the queued andun-processed requests waiting for the FPD 118. New requests requiringLogic C are processed by the FPD 120. In a non-limiting example, if theimplementation has one queue for each FPD 118 and 120, and, for Logic C,there are two queues, the first queue for the requests to be run on theFPD 118 and the second queue for the requests to be run on the FPD 120,the requests in the first queue is merged into the second queue based onthe time the request was added to the queue.

In another non-limiting example, if the implementation has one queue forall FPDs running Logic C and there is one queue where requests areretrieved by a dispatcher and sent to the FPDs 118 and 120, thedispatcher detects or notifies that the FPD 118 is offline and no longerdispatches future requests to FPD 118. In another non-limiting example,if the FPD 118 has been processing requests belonging to the sameworkload, the state information, such as the next memory location of thedata to be process, is kept and used by the FPD 120 when processing theremaining requests belonging to the same workload.

The processing system 100 then loads a new set of logic (i.e., Logic B)to FPD 118. As illustrated in FIG. 1B, FPD 118 is reprogrammed withLogic B, thereby enabling FPD 118 to execute workloads of the secondtype. The FPD 118 is then brought online to begin executing aspecialized workload of the second type received from the processingsystem 100. In a non-limiting example, if the implementation has onequeue for each FPD, then additional queues can be created for the FPD118 reprogrammed with logic B. A subset of existing requests waiting inqueues belonging to the FPDs 114 and 116 can be moved to the queuebelong to the FPD 118. In another non-limiting example, if theimplementation has one queue for all FPDs running Logic B, thedispatcher detects or notifies that the FPD 118 is available anddispatcher can dispatch requests from the queue to the FPD 118 forprocessing.

FIG. 2 illustrates a flow diagram of a method 200 for reprogramming anFPD on demand according to examples of the present disclosure. Themethod 200 may be performed, for example, by a processing system such asthe processing system 100 of FIG. 1A and FIG. 1B, by the processingsystem 20 of FIG. 4, or by another suitable processing system. Themethod 200 starts at block 202 and continues to block 204. It should beappreciated that, although the method 200 is described with reference tofield programmable devices, it should be appreciated that the FPDs maybe one of a field-programmable gate array, a programmable read-onlymemory, or a programmable logic device. The method 200 starts at block202 and continues to block 204.

At block 204, the method 200 includes identifying, by a processingdevice, a first FPD as being over utilized, wherein the first FPD isconfigured with a first set of computer readable instructions to performa first workload type.

At block 206, the method 200 includes, responsive to identifying thefirst FPD that is over utilized, identifying, by the processing device,a second FPD that is underutilized, wherein the second FPD is configuredwith a second set of computer readable instructions different from thefirst set of computer readable instructions to perform a second workloadtype. If no FPD is being over utilized, the method 200 may return toidentify a first FPD as being over utilized at block 204, such as afterwaiting a delay time.

At block 208, the method 200 includes determining whether to reprogramthe second FPD with the first set of computer readable instructions. Insome examples, determining whether to reprogram the second FPD with thefirst set of computer readable instructions is based on at least one ofa priority of a workload type, a current performance of the first FPD, acurrent performance of the second FPD, a projected performance of thefirst FPD after the second FPD is reprogrammed, a projected performanceof the second FPD after the second FPD is reprogrammed, a demand level,a comparison of FPD performance before and after the second FPD isreprogrammed, a licensing requirement, a cost factor associated with anadditional FPD running first set of computer readable instruction,another cost factor associated with not running second set of computerreadable instruction on the second FPD, an electricity or powerconsumption and management requirement, compatibility between second FPDand first set of computer readable instructions, and a redundancyrequirement.

As a non-limiting example, workload 1 is running on a first FPD with afirst set of computer readable instructions, and the first FPDover-utilized at 100% with multiple requests waiting in queue. Workload2 is running on a second FPD and a third FPD with a second set ofcomputer readable instructions. The second and third FPDs are notover-utilized (e.g., they are at 80% for each of the FPDs or at 160%combined for both FPDs). It may be projected that after the second FPDis reprogrammed with the second set of computer readable instructions,each of the first and second FPD each will be at 60% utilization or 120%for both FPDs on behalf of workload 1. By comparing the projectedoverall FPD utilization of workload 1 at 120% with the overall FPDsutilization of workload 2 at 160%, it might be determined that thesecond FPD should not be reprogrammed with the first set of computerreadable instructions. The above example is not limited to and can beextended to multiple workloads running on the first FPD with first setof computer readable instructions.

As a non-limiting example to determine utilization, the availablecapacity of a FPD can be calculated or estimated based on an “amount ofadditional work” it can process without causing the average number ofqueued requests to increase over a threshold. Then, the utilization canbe calculated based on the available capacity over the total capacity,which can be calculated using the currently utilized capacity plus theavailable capacity.

As another non-limiting example, workload 1 running on a first FPD iscurrently having a response time of 5 seconds, while workload 2 runningon a second FPD and a third FPD is currently having a response time of 2seconds. It might be projected that after the second FPD is reprogrammedwith the first set of computing readable instructions, workload 1 willhave a response time of 3 seconds, while workload 2 will have a responsetime of 3 seconds.

As another non-limiting example, licensing of workload 1 might be billedon the utilization of the FPD, while software licensing of workload 2might be billed on behalf of the entire FPD (i.e., assuming that the FPDis fully utilized for a workload). In the example above, even thoughoverall FPD utilization of workload 1 is at 120%, while overall FPDsutilization of workload 2 at 160%, the licensing of workload 1 runningon two FPDs is cheaper than workload 2 running on two FPDs. In addition,it might not be worthwhile to pay for the licensing cost of the entireFPD for workload 2, when only 60% of the FPD will be utilized (when thethird FPD can be running at 100% utilized). Therefore, it can be decidedthat the second FPD should be reprogrammed to the first set of computerreadable instructions. On the other hand, it might be determined thatfor workload 2, if more than 80% of the second FPD will be utilized(when the third FPD is running at 100% utilized), then the cost ofcharging for the entire FPD is reasonable.

The current and projected result (utilization, response time, licensingcost, etc.) can be compared against a specified performance policy orservice level agreement, and the reprogramming action can beautomatically triggered. The current and projected overall utilizationcan also be reported to the user, and the user can further analyze andmanually invoke reprogramming action. The current and projected overallutilization can also be reported to and utilized by a workloadmanagement software. The workload management software can also takeother performance management actions, such as workload migration,capacity upgrade on demand, into consideration.

At block 210, the method 200 includes, responsive to determining toreconfigure the second FPD with the first set of computer readableinstructions, stopping the second FPD from performing a workload of thesecond workload type. Stopping the second FPD from performing theworkload of the second workload type may include completing an executingworkload of the second workload type before stopping the second FPD fromperforming an additional workload of the second workload type. Thisenables an executing workload to complete, but the second FPD may notaccept additional workloads.

At block 212, the method 200 includes moving the workload of the secondworkload type to another FPD configured to perform the workload of thesecond workload type. In another FPD to move the workload to does notexist or is not available, the workload may be executed on a generalpurpose processor (i.e., the processor 102 of FIGS. 1A and 1B) using acomputer executable code if available. In another example, the workloadcan be migrated to another processing system that has an FPD binaryprogrammed in one of the FPDs suitable for performing the workload.

At block 214, the method 200 includes reprogramming the second FPD withthe first set of computer readable instructions to perform the firstworkload type. In examples, reprogramming the second field programmabledevice with the first set of computer readable instructions to performthe first workload type includes: bringing the second field programmabledevice offline; loading the first set of computer readable instructionsto the second field programmable device; and bringing the second fieldprogrammable device online.

The method 200 continues to block 216 and ends. In some examples, themethod looks back to the start 202 and begins identifying over utilizedFPDs again at block 204.

Additional processes also may be included. For example, the method 200may include executing a workload of the first workload type on thesecond FPD after bringing the second field programmable device online.

It should be understood that the processes depicted in FIG. 2 representillustrations, and that other processes may be added or existingprocesses may be removed, modified, or rearranged without departing fromthe scope and spirit of the present disclosure.

FIG. 3 illustrates a flow diagram of a method 300 for reprogramming aFPD on demand according to examples of the present disclosure. Themethod 300 may be performed, for example, by a processing system such asthe processing system 100 of FIG. 1A and FIG. 1B, by the processingsystem 30 of FIG. 4, or by another suitable processing system. Themethod 300 starts at block 302 and continues to block 304. It should beappreciated that, although the method 300 is described with reference tofield programmable devices, it should be appreciated that the FPDs maybe one of a field-programmable gate array, a programmable read-onlymemory, or a programmable logic device. The method 300 starts at block302 and continues to block 304.

At block 304, the method 300 includes identifying, by a processingdevice, a first FPD as being over utilized, wherein the first FPD isconfigured with a first set of computer readable instructions to performa first workload type.

At block 306, the method 300 includes, responsive to identifying thefirst FPD that is over utilized, identifying, by the processing device,a second FPD that is underutilized, wherein the second FPD is configuredwith a second set of computer readable instructions different from thefirst set of computer readable instructions to perform a second workloadtype.

At block 308, the method 300 includes determining whether to reprogramthe second FPD with the first set of computer readable instructions. Insome examples, determining whether to reprogram the second FPD with thefirst set of computer readable instructions is based on at least one ofa priority of a workload type, a performance of the first FPD, aperformance of the second FPD, a demand level, and a redundancyrequirement.

In one example, a redundancy requirement may be implemented as follows,with reference to FIG. 1A. For example, a workload 1 is running on FPD110 and FPD 112 and a workload 2 is running on FPD 114 and FPD 116. IfFPD 114 fails, and in order to provide redundancy for workload 2, FPD118 may be reprogramed with logic B for the execution of workload 2.

At block 310, the method 300 includes, responsive to determining toreconfigure the second FPD with the first set of computer readableinstructions, stopping the second FPD from performing a workload of thesecond workload type. Stopping the second FPD from performing theworkload of the second workload type may include completing an executingworkload of the second workload type before stopping the second FPD fromperforming an additional workload of the second workload type. Thisenables an executing workload to complete, but the second FPD may notaccept additional workloads.

At block 312, the method 300 includes moving the workload of the secondworkload type to another FPD configured to perform the workload of thesecond workload type.

At block 314, the method 300 includes bringing the second FPD offline.

At block 316, the method 300 includes loading the first set of computerreadable instructions to the second FPD. The first set of computerreadable instructions may be received from the processing system, forexample.

At block 318, the method 300 includes bringing the second FPD online.The method 300 continues to block 320 and ends. In some examples, themethod looks back to the start 302 and begins identifying over utilizedFPDs again at block 304.

Additional processes also may be included. For example, the method 300may include executing a workload of the first workload type on thesecond FPD after bringing the second field programmable device online.

It should be understood that the processes depicted in FIG. 3 representillustrations, and that other processes may be added or existingprocesses may be removed, modified, or rearranged without departing fromthe scope and spirit of the present disclosure.

It is understood in advance that the present disclosure is capable ofbeing implemented in conjunction with any other type of computingenvironment now known or later developed. For example, FIG. 4illustrates a block diagram of a processing system 20 for implementingthe techniques described herein. In examples, processing system 20 hasone or more central processing units (processors) 21 a, 21 b, 21 c, etc.(collectively or generically referred to as processor(s) 21 and/or asprocessing device(s)). In aspects of the present disclosure, eachprocessor 21 may include a reduced instruction set computer (RISC)microprocessor. Processors 21 are coupled to system memory (e.g., randomaccess memory (RAM) 24) and various other components via a system bus33. Read only memory (ROM) 22 is coupled to system bus 33 and mayinclude a basic input/output system (BIOS), which controls certain basicfunctions of processing system 20.

Further illustrated are an input/output (I/O) adapter 27 and acommunications adapter 26 coupled to system bus 33. I/O adapter 27 maybe a small computer system interface (SCSI) adapter that communicateswith a hard disk 23 and/or a tape storage drive 25 or any other similarcomponent. I/O adapter 27, hard disk 23, and tape storage device 25 arecollectively referred to herein as mass storage 34. Operating system 40for execution on processing system 20 may be stored in mass storage 34.A network adapter 26 interconnects system bus 33 with an outside network36 enabling processing system 20 to communicate with other such systems.

A display (e.g., a display monitor) 35 is connected to system bus 33 bydisplay adaptor 32, which may include a graphics adapter to improve theperformance of graphics intensive applications and a video controller.In one aspect of the present disclosure, adapters 26, 27, and/or 32 maybe connected to one or more I/O busses that are connected to system bus33 via an intermediate bus bridge (not shown). Suitable I/O buses forconnecting peripheral devices such as hard disk controllers, networkadapters, and graphics adapters typically include common protocols, suchas the Peripheral Component Interconnect (PCI). Additional input/outputdevices are shown as connected to system bus 33 via user interfaceadapter 28 and display adapter 32. A keyboard 29, mouse 30, and speaker31 may be interconnected to system bus 33 via user interface adapter 28,which may include, for example, a Super I/O chip integrating multipledevice adapters into a single integrated circuit.

In some aspects of the present disclosure, processing system 20 includesa graphics processing unit 37. Graphics processing unit 37 is aspecialized electronic circuit designed to manipulate and alter memoryto accelerate the creation of images in a frame buffer intended foroutput to a display. In general, graphics processing unit 37 is veryefficient at manipulating computer graphics and image processing, andhas a highly parallel structure that makes it more effective thangeneral-purpose CPUs for algorithms where processing of large blocks ofdata is done in parallel.

Thus, as configured herein, processing system 20 includes processingcapability in the form of processors 21, storage capability includingsystem memory (e.g., RAM 24), and mass storage 34, input means such askeyboard 29 and mouse 30, and output capability including speaker 31 anddisplay 35. In some aspects of the present disclosure, a portion ofsystem memory (e.g., RAM 24) and mass storage 34 collectively store anoperating system such as the AIX® operating system from IBM Corporationto coordinate the functions of the various components shown inprocessing system 20.

The present techniques may be implemented as a system, a method, and/ora computer program product. The computer program product may include acomputer readable storage medium (or media) having computer readableprogram instructions thereon for causing a processor to carry outaspects of the present disclosure.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present disclosure may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some examples, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present disclosure.

Aspects of the present disclosure are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to aspects of thepresent disclosure. It will be understood that each block of theflowchart illustrations and/or block diagrams, and combinations ofblocks in the flowchart illustrations and/or block diagrams, can beimplemented by computer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousaspects of the present disclosure. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The descriptions of the various examples of the present disclosure havebeen presented for purposes of illustration, but are not intended to beexhaustive or limited to the embodiments disclosed. Many modificationsand variations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the described techniques.The terminology used herein was chosen to best explain the principles ofthe present techniques, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the techniquesdisclosed herein.

What is claimed is:
 1. A computer-implemented method for reprogramming afield programmable device on demand, the method comprising: identifying,by a processing device, a first field programmable device as being overutilized, wherein the first field programmable device is configured witha first set of computer readable instructions to perform a firstworkload type, wherein the first field programmable device is identifiedas being over utilized when a number of requests waiting to be executedby the first field programmable device exceeds a threshold; responsiveto identifying the first field programmable device that is overutilized, identifying, by the processing device, a second fieldprogrammable device that is underutilized, wherein the second fieldprogrammable device is configured with a second set of computer readableinstructions different from the first set of computer readableinstructions to perform a second workload type; determining whether toreprogram the second field programmable device with the first set ofcomputer readable instructions; responsive to determining to reprogramthe second field programmable device with the first set of computerreadable instructions, stopping the second field programmable devicefrom performing a workload of the second workload type; andreprogramming the second field programmable device with the first set ofcomputer readable instructions by loading the first set of computerreadable instructions to the second field programmable device to causethe second field programmable device to perform the first workload typeinstead of the second workload type.
 2. The computer-implemented methodof claim 1, wherein reprogramming the second field programmable devicewith the first set of computer readable instructions to perform thefirst workload type further comprises: bringing the second fieldprogrammable device offline; loading the first set of computer readableinstructions to the second field programmable device subsequent tobringing the second field programming device offline; and bringing thesecond field programmable device online subsequent to the loading. 3.The computer-implemented method of claim 2, further comprising executinga workload of the first workload type on the second field programmabledevice after bringing the second field programmable device online. 4.The computer-implemented method of claim 1, wherein determining whetherto reprogram the second field programmable device with the first set ofcomputer readable instructions is based on at least one of a priority ofa workload type, a performance of the first field programmable device, aperformance of the second field programmable device, a demand level, anda redundancy requirement.
 5. The computer-implemented method of claim 1,wherein the field programmable device is one of a field-programmablegate array, a programmable read-only memory, or a programmable logicdevice.
 6. The computer-implemented method of claim 1, wherein loadingthe first set of computer readable instructions to the second fieldprogrammable device comprises receiving the first set of computerreadable instructions from the processing device.
 7. Thecomputer-implemented method of claim 1, wherein stopping the secondfield programmable device from performing the workload of the secondworkload type further comprises completing an executing workload of thesecond workload type before stopping the second field programmabledevice from performing an additional workload of the second workloadtype.
 8. The computer-implemented method of claim 1, wherein determiningwhether to reprogram the second field programmable device with the firstset of computer readable instructions further comprises: considering animpact to the first field programmable device as a result ofreprogramming the second field programmable device with the first set ofcomputer readable instructions; and considering an impact to other fieldprogrammable devices as a result of reprogramming the second fieldprogrammable device with the first set of computer readableinstructions.
 9. A system for reprogramming a field programmable deviceon demand, the system comprising: a memory having computer readableinstructions; and a processing device for executing the computerreadable instructions, the computer readable instructions comprising:identifying a first field programmable device as being over utilized,wherein the first field programmable device is configured with a firstset of computer readable instructions to perform a first workload type,wherein the first field programmable device is identified as being overutilized when a number of requests waiting to be executed by the firstfield programmable device exceeds a threshold; responsive to identifyingthe first field programmable device that is over utilized, identifying asecond field programmable device that is underutilized, wherein thesecond field programmable device is configured with a second set ofcomputer readable instructions different from the first set of computerreadable instructions to perform a second workload type; determiningwhether to reprogram the second field programmable device with the firstset of computer readable instructions; responsive to determining toreprogram the second field programmable device with the first set ofcomputer readable instructions, stopping the second field programmabledevice from performing a workload of the second workload type; andreprogramming the second field programmable device with the first set ofcomputer readable instructions by loading the first set of computerreadable instructions to the second field programmable device to causethe second field programmable device to perform the first workload typeinstead of the second workload type.
 10. The system of claim 9, whereinreprogramming the second field programmable device with the first set ofcomputer readable instructions to perform the first workload typefurther comprises: bringing the second field programmable deviceoffline; loading the first set of computer readable instructions to thesecond field programmable device subsequent to bringing the second fieldprogramming device offline; and bringing the second field programmabledevice online subsequent to the loading.
 11. The system of claim 10, thecomputer readable instructions further comprising executing a workloadof the first workload type on the second field programmable device afterbringing the second field programmable device online.
 12. The system ofclaim 9, wherein determining whether to reprogram the second fieldprogrammable device with the first set of computer readable instructionsis based on at least one of a priority of a workload type, a performanceof the first field programmable device, a performance of the secondfield programmable device, a demand level, and a redundancy requirement.13. The system of claim 9, wherein the field programmable device is oneof a field-programmable gate array, a programmable read-only memory, ora programmable logic device.
 14. The system of claim 9, wherein loadingthe first set of computer readable instructions to the second fieldprogrammable device comprises receiving the first set of computerreadable instructions from the processing device.
 15. The system ofclaim 9, wherein stopping the second field programmable device fromperforming the workload of the second workload type further comprisescompleting an executing workload of the second workload type beforestopping the second field programmable device from performing anadditional workload of the second workload type.
 16. The system of claim9, wherein determining whether to reprogram the second fieldprogrammable device with the first set of computer readable instructionsfurther comprises: considering an impact to the first field programmabledevice as a result of reprogramming the second field programmable devicewith the first set of computer readable instructions; and considering animpact to other field programmable devices as a result of reprogrammingthe second field programmable device with the first set of computerreadable instructions.
 17. A computer program product for reprogramminga field programmable device on demand, the computer program productcomprising: a computer readable storage medium having programinstructions embodied therewith, the program instructions executable bya processing device to cause the processing device to: identifying afirst field programmable device as being over utilized, wherein thefirst field programmable device is configured with a first set ofcomputer readable instructions to perform a first workload type, whereinthe first field programmable device is identified as being over utilizedwhen a number of requests waiting to be executed by the first fieldprogrammable device exceeds a threshold; responsive to identifying thefirst field programmable device that is over utilized, identify a secondfield programmable device that is underutilized, wherein the secondfield programmable device is configured with a second set of computerreadable instructions different from the first set of computer readableinstructions to perform a second workload type; determine whether toreprogram the second field programmable device with the first set ofcomputer readable instructions; responsive to determining to reprogramthe second field programmable device with the first set of computerreadable instructions, stop the second field programmable device fromperforming a workload of the second workload type; and reprogram thesecond field programmable device with the first set of computer readableinstructions by loading the first set of computer readable instructionsto the second field programmable device to cause the second fieldprogrammable device to perform the first workload type instead of thesecond workload type.
 18. The computer program product of claim 17,wherein reprogramming the second field programmable device with thefirst set of computer readable instructions to perform the firstworkload type further comprises: bringing the second field programmabledevice offline; loading the first set of computer readable instructionsto the second field programmable device subsequent to bringing thesecond field programming device offline; and bringing the second fieldprogrammable device online subsequent to the loading.
 19. The computerprogram product of claim 18, the program instructions further causingthe processing device to execute a workload of the first workload typeon the second field programmable device after bringing the second fieldprogrammable device online.
 20. The computer program product of claim17, wherein determining whether to reprogram the second fieldprogrammable device with the first set of computer readable instructionsis based on at least one of a priority of a workload type, a performanceof the first field programmable device, a performance of the secondfield programmable device, a demand level, and a redundancy requirement.